@magoo_it said in PHP error after reboot: It seems that today is not my best day on IT ... well better days will come. aww, don't be so hard on yourself. I have to keep a sticky on the Reddit group about this tool because it seems very few people there know about it, either.

@stephenw10 Thanks! Regards.

As shown in that thread you can edit /etc/skel/dot.tcshrc which is where that file is created from. However that still might be lost at a firmware upgrade. I created a feature request for this: https://redmine.pfsense.org/issues/14746 Steve

Hmm, maybe something else was using some bandwidth?

Nice catch. And relatively easy fix.

For some weird reason, I though that L2 VPN was only used for remote access, not for peer to peer. I've successfuly migrated from Vxlan to Openvpn. Thanks for your help

With the mitigations in place the C3558 will do 1Gbps, I tested that. So pretty much anything recent.

@stephenw10 said in Windstream fiber -> Adtran 411 -> PfSense slow upload speed: The WAN flapping seems like a different issue to the upload speed throttling. I would try swapping the WAN and LAN NICs to see if it's something to one of them. Has the WAN always flapped like that? Apologies for the delay in response. The WAN has only ever flapped when I used the Asrock NUC BOX-1360P/D5 Intel 2.5 Gbps NICs to connect to my fiber ONT box. It did not work with the Aruba switch either. The WAN continued to flap up and down repeatedly and I was not getting the full upload speeds. I ended up replacing the Asrock NUC BOX-1360P/D5 PC with another PC with a PCIe express slot and put in an Intel X710-T2L card. I reran the connection speed test with the EdgeSwitch and finally got synchronous upload and download speeds of ~950 Mbps. Inspecting the PFSense interface logs, it no longer reported "In/out errors" when the test ran. In addition, the WAN flapping has stopped, and it's been online for more than 10 days. I also tried the Intel X710-T2L card with the new Aruba switch, and it is getting synchronous upload and download speeds of ~950 Mbps. Either my Asrock NUC BOX-1360P/D5 had a bad NIC, or something was going on, but I did not want to deal with the problems anymore. Thank you for the assistance and guidance you provided me as I tried to troubleshoot this problem @stephenw10

I know this topic is quite old, but it was the only one I could find that had my exact issue. In my case I accidentally enabled the Proxmox firewall on the VM I was trying to ping, so make sure to double check if you enabled a firewall, it could have saved my multiple hours of headache...

You can trigger a notification using php like: require_once('notices.inc'); file_notice(1,"Test"); That will use all the configured notification methods including Telegram if it's set. Steve

@Gertjan Hello, Thank you for your detailed answer. I have tried to even fresh installed the VM with NIC passthrough out of the box but PFsenese takes at least 5-10 min to resolve DNS. AFter the initial time my devices connect to it can resolve DNS. However, if I leave it over night or in the morning when I turn on my computer again. PFsense is still running 24/7. It takes at least about 5 min before every device can resolve DNS again. As you have suggested, I think it may lies at my Proxmox server. I may have to install it barebones. Thank you again for your time.

@stephenw10 I dunno.... no clue, I rebuilt the 2 hyper-v adapters on the pfsense vm, the external and internal... and of course now it works. Oh well... Thanks for responding to my question!!!

Yup, the local issue was resolved. Should be good now.

Yup, local v6 routing issue has been resolved.

Ah, interesting. You might check out general IPv6 connectivity from another client then.

@stephenw10 Thank you so much.

@stephenw10 It works ! Thanks !

TLDR; We're using pi-hole for DNS, and let pfSense do all the DHCP, routing and firewalling tasks. This solution suits our use case, and has been working well for a long time. YMMV.

@tapufd said in SMTP Notifications not working anymore: I was reading some other community topics about slowness of Package Manager and Update, which I was also experiencing. smtp.office365.com has a zillion local access points, so there is always one 'nearby' (Microsoft is a big company). For me, all nearby IPv6 is working well. If IPv6 is suspected, go Ipv4 mode : telnet -4 smtp.office365.com 587 and test the other one also telnet -6 smtp.office365.com 587 If you actually use IPv6 (have a working IPv6 connection). edit : ah, ok, didn't saw your latest port. Yeap, it is probably an IPv6 issue. Where are you ? Where is - as far as you know - is the smtp.office365.com for you ?